<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Subsections</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
TITLE="DataparkSearch Engine 4.54"
HREF="index.en.html"><LINK
REL="PREVIOUS"
TITLE="Oracle notes"
HREF="dpsearch-oracle.en.html"><LINK
REL="NEXT"
TITLE="Categories"
HREF="dpsearch-categories.en.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
HREF="datapark.css"><META
NAME="Description"
CONTENT="DataparkSearch - Full Featured Web site Open Source Search Engine Software over the Internet and Intranet Web Sites Based on SQL Database. It is a Free search software covered by GNU license."><META
NAME="Keywords"
CONTENT="shareware, freeware, download, internet, unix, utilities, search engine, text retrieval, knowledge retrieval, text search, information retrieval, database search, mining, intranet, webserver, index, spider, filesearch, meta, free, open source, full-text, udmsearch, website, find, opensource, search, searching, software, udmsearch, engine, indexing, system, web, ftp, http, cgi, php, SQL, MySQL, database, php3, FreeBSD, Linux, Unix, DataparkSearch, MacOS X, Mac OS X, Windows, 2000, NT, 95, 98, GNU, GPL, url, grabbing"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000C4"
VLINK="#1200B2"
ALINK="#C40000"
><!--#include virtual="body-before.html"--><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>DataparkSearch Engine 4.54: Reference manual</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="dpsearch-oracle.en.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="dpsearch-categories.en.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="CHAPTER"
><H1
><A
NAME="SUBSECTIONS"
></A
>Chapter 6. Subsections</H1
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
>6.1. <A
HREF="dpsearch-subsections.en.html#TAGS"
>Tags</A
></DT
><DT
>6.2. <A
HREF="dpsearch-categories.en.html"
>Categories</A
></DT
></DL
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="TAGS"
>6.1. Tags</A
></H1
><A
NAME="AEN3948"
></A
><P
>Tag is a special parameter which can be given for a set
of documents. The main purpose of tags is to join a number of
documents into one group and then while doing search to select a group
of documents to search through. </P
><A
NAME="AEN3951"
></A
><P
>You should use <B
CLASS="COMMAND"
>Tag</B
> command of
<TT
CLASS="FILENAME"
>indexer.conf</TT
> to assign some tag value for a server
or server subset by putting it before corresponding <B
CLASS="COMMAND"
>Server/Realm/Subnet</B
> command. While doing search you can specify tag value to
search through documents which tag matches given parameter with
<CODE
CLASS="PARAMETER"
>t=xxx</CODE
> parameter, which can be passed from HTML
form. Take a look into <A
HREF="dpsearch-subsections.en.html#TAG_CMD"
>Section 6.1.1</A
>&#62;, <TT
CLASS="FILENAME"
>indexer.conf-dist</TT
> and
<TT
CLASS="FILENAME"
>search.htm-dist</TT
> for explanation and
examples.</P
><DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
>For dbmode cache you need to have the following section defined in your
<TT
CLASS="FILENAME"
>sections.conf</TT
> file:
<PRE
CLASS="PROGRAMLISTING"
>Section tag 0 64</PRE
>
in overall you need to have the section 'tag' defined with non-zero maximum length.</P
></BLOCKQUOTE
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="TAG_CMD"
>6.1.1. <B
CLASS="COMMAND"
>Tag</B
> command</A
></H2
><A
NAME="AEN3969"
></A
><PRE
CLASS="PROGRAMLISTING"
>Tag &lt;string&gt;</PRE
><P
>Use this field for your own purposes. For example for grouping
some servers into one group, etc... During search you'll be able to
limit URLs to be searched through by their tags.
Can be set multiple times before <B
CLASS="COMMAND"
>Server</B
> command and
takes effect till the end of config file or till next <B
CLASS="COMMAND"
>Tag</B
> command.
Default values is an empty string.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="TAGIF_CMD"
>6.1.2. <B
CLASS="COMMAND"
>TagIf</B
> command</A
></H2
><A
NAME="AEN3979"
></A
><PRE
CLASS="PROGRAMLISTING"
>TagIf &lt;tag&gt; [Match|NoMatch] [NoCase|Case] [String|Regex] [loose] &lt;section&gt; &lt;arg&gt; [&lt;arg&gt; ... ]</PRE
><P
>Mark document by &lt;tag&gt; tag, if the value of <CODE
CLASS="OPTION"
>section</CODE
> match the <CODE
CLASS="OPTION"
>arg</CODE
> pattern given.
The meaning of first three optional parameters are exactly the same 
as for the <B
CLASS="COMMAND"
>Allow</B
> command (see <A
HREF="dpsearch-indexcmd.en.html#ALLOW_CMD"
>Section 3.10.14</A
>&#62;). Optional parameter <CODE
CLASS="OPTION"
>loose</CODE
> specify
to do not override the tag value if it has been already set from server parameters.</P
><P
>Example
<PRE
CLASS="PROGRAMLISTING"
>TagIf Docs regex Title Manual</PRE
></P
><P
>You can use template meta-variables (as for example, $(Title), $(Last-Modified), etc.) in &lt;tag&gt; tag. An example below
shows how to assign hostname from URL as a tag for any document indexed:
<PRE
CLASS="PROGRAMLISTING"
>TagIf $(url.host) match url.host *</PRE
></P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="TAGS-SQL"
>6.1.3. Tags in SQL version</A
></H2
><P
>Tag type is CHAR. CHAR type allows to use some nice
features. You can use '_' and '%' LIKE wildcards in tag parameter
when doing search. It makes possible that tag, like a category,  does
support an idea of nesting. For example, documents with tag value "AB"
can be found with both "A%" and "AB" tag limits.</P
><P
>Tags also give a way to make an URL a member of
multiple tag selections. Playing with LIKE wildcards you can easily
create two or more groups.</P
><P
>For example, tag "ABCDE" is the member of at least these selections:
		<PRE
CLASS="PROGRAMLISTING"
>_BCDE
A_CDE
AB_DE
ABC_E
ABCD_</PRE
></P
><DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
>If you have big enough database and
often use tag limits, it is useful to create an index by field "tag"
in "server" table. This index is not created by default.
<PRE
CLASS="PROGRAMLISTING"
>CREATE INDEX srv_tag ON "server" ("tag");</PRE
></P
><P
>By default, the length of tag field in url table is limited by 16 characters.
If you need more, increase this length before DB creating.</P
></BLOCKQUOTE
></DIV
><DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
>For cache storage mode, you can use SQL's wildcards only with <B
CLASS="COMMAND"
>indexer</B
>.</P
></BLOCKQUOTE
></DIV
></DIV
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="dpsearch-oracle.en.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.en.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="dpsearch-categories.en.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Oracle notes</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Categories</TD
></TR
></TABLE
></DIV
><!--#include virtual="body-after.html"--></BODY
></HTML
>